This seems out of sync with the discussion in #4179, no?

The PR should resolve #4179. It's not the implementation of the last idea (with the mixins), which intends to provide another public API for the ripples.

In my opinion, if we should expose the ripple instance, then it should be really the MatRipple and no wrapper, that just provides a nicer API.

Since there is a overview file for the ripple now, I think that it would be fine just exposing the instance. Also, as I mentioned in #9170, we can add a guide that shows how to control ripples of components that expose the instance.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}